cleanup: upstream dropped amx-transpose functionality #148338
Merged
+0
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See also LLVM change 5322fb626820. Looks like this was just removed entirely.
rustbot
added
S-waiting-on-review
rustbot
added
the
llvm-main
|
#126622 was tracking the support. The change looks sane to me given Intel is dropping it everywhere. It'd great to get this or another workaround landed soon, since its blocking Fuchsia from getting new toolchain candidates, and I imagine Chrome and Android will hit this soon as well. |
|
lgtm. @bors r+ |
bors
added
S-waiting-on-bors
3 tasks
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Nov 1, 2025
…orkingjubilee cleanup: upstream dropped amx-transpose functionality See also LLVM change 5322fb626820. Looks like this was just removed entirely. It seems a little bad to just drop it, but I don't see an easy way to conditionalize this and if it's really just Gone and we marked it as unstable (which it looks like we did?) I guess we should just dump it. `@rustbot` label llvm-main
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Nov 1, 2025
…orkingjubilee cleanup: upstream dropped amx-transpose functionality See also LLVM change 5322fb626820. Looks like this was just removed entirely. It seems a little bad to just drop it, but I don't see an easy way to conditionalize this and if it's really just Gone and we marked it as unstable (which it looks like we did?) I guess we should just dump it. ``@rustbot`` label llvm-main
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this pull request
Nov 1, 2025
…orkingjubilee cleanup: upstream dropped amx-transpose functionality See also LLVM change 5322fb626820. Looks like this was just removed entirely. It seems a little bad to just drop it, but I don't see an easy way to conditionalize this and if it's really just Gone and we marked it as unstable (which it looks like we did?) I guess we should just dump it. ```@rustbot``` label llvm-main
This was referenced Nov 1, 2025
bors
added a commit
that referenced
this pull request
Nov 1, 2025
Rollup of 10 pull requests Successful merges: - #135602 (Tweak output of missing lifetime on associated type) - #139751 (Implement pin-project in pattern matching for `&pin mut|const T`) - #142682 (Update bundled musl to 1.2.5) - #148171 (Simplify code to generate line numbers in highlight) - #148263 (Unpin `libc` and `rustix` in `compiler` and `rustbook`) - #148301 ([rustdoc search] Include extern crates when filtering on `import`) - #148330 (Don't require dlltool with the dummy backend on MinGW) - #148338 (cleanup: upstream dropped amx-transpose functionality) - #148340 (Clippy subtree update) - #148343 (`nonpoison::Condvar` should take `MutexGuard` by reference) r? `@ghost` `@rustbot` modify labels: rollup
bors
added a commit
that referenced
this pull request
Nov 1, 2025
Rollup of 10 pull requests Successful merges: - #135602 (Tweak output of missing lifetime on associated type) - #139751 (Implement pin-project in pattern matching for `&pin mut|const T`) - #142682 (Update bundled musl to 1.2.5) - #148171 (Simplify code to generate line numbers in highlight) - #148263 (Unpin `libc` and `rustix` in `compiler` and `rustbook`) - #148301 ([rustdoc search] Include extern crates when filtering on `import`) - #148330 (Don't require dlltool with the dummy backend on MinGW) - #148338 (cleanup: upstream dropped amx-transpose functionality) - #148340 (Clippy subtree update) - #148343 (`nonpoison::Condvar` should take `MutexGuard` by reference) r? `@ghost` `@rustbot` modify labels: rollup
rust-timer
added a commit
that referenced
this pull request
Nov 1, 2025
Rollup merge of #148338 - durin42:llvm-22-amx-transpose, r=workingjubilee cleanup: upstream dropped amx-transpose functionality See also LLVM change 5322fb626820. Looks like this was just removed entirely. It seems a little bad to just drop it, but I don't see an easy way to conditionalize this and if it's really just Gone and we marked it as unstable (which it looks like we did?) I guess we should just dump it. ````@rustbot```` label llvm-main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See also LLVM change 5322fb626820. Looks like this was just removed entirely.
It seems a little bad to just drop it, but I don't see an easy way to conditionalize
this and if it's really just Gone and we marked it as unstable (which it looks like
we did?) I guess we should just dump it.
@rustbot label llvm-main